Authorization/Deposit Interface Setup

Purpose: This topic describes the setup required to communicate with a service bureau for authorization and deposit settlement.

In this topic:

• System Control Values

• Number Assignment Value

• Service Bureau Settings

• Order Types

• Pay Types

• Pick Slip Generation

• Integration Layer Jobs

• Notify Property Settings

• Logging Property Settings

For more information: See:

• Stored Value Card Overview and Setup for more information on the setup required to process a stored value card.

• The CWIntegrate Site Reference for more information on the processing that occurs when you use a CWIntegrate site to handle communication and mapping between CWSerenade and a service bureau.

• Processing Authorizations and Deposits Using Point-to-Point Communication for more information on the setup required to processing transactions directly to the service bureau in its own message format.

System Control Values

System Control Value	Description
Use Auto Authorization Interface (C14)	Defines whether you are using the interface to electronically transmit authorization and deposit information for your credit card orders to an authorization service.
Consolidated Invoice (B49)	Determines whether a separate authorization and invoice will be created for each pick associated with an order, or if only one authorization and invoice will be created per shipment.
On-line Authorizations (B89)	Defines whether the system performs online credit card authorization during order entry. See Performing Online Credit Card Authorizations for an overview and required setup.
Maximum Number of Retries on Credit Card Orders (E74)	Determines the maximum number of times to attempt to authorize an order before flagging the order for cancellation.
Credit Card Authorization AVS Hold Exemption/Bypass (E61)	Specifies how to handle orders put on the same type of AVS hold a second time after you have released them. If you select this field, the system will not hold an order more than once for the same AVS response code if, for example, you need to reauthorize the order again because a backordered item is now available for shipment.
Default Credit Card Authorization Number for Soft Declines (F93)	Defines the authorization number the system defaults when a credit card authorization is declined but is under a specified dollar amount.
Use Credit Card Vendor Response Entity Ship Via Dollar Limits (F94)	Defines whether the system performs an edit against a credit card vendor response to determine if the dollar amount for the credit card authorization exceeds the dollar limit defined for the ship via on the order.
Authorize Full Amount During Order Entry (G99)	Defines whether the credit card on the order is authorized for the entire dollar amount defined for the card or the shippable amount defined for the card when you perform online authorization during order entry.
Authorization Number for Authorizations Under $1.00 (I08)	Defines the authorization number the system automatically applies to credit cards that require authorizations that are under one dollar.
Online Auth Verification Only (I96)	Defines whether the system processes online authorizations for $1.00 for the purpose of validating the card. During batch authorizations, the system authorizes the card for the shippable dollar amount and voids the online authorization for $1.00.

Number Assignment Value

Number Assignment	Description
Transaction Sequence #	Assigns the next available number to the credit card authorization.
Batch Auth File Trace Number	Assigns the next available number to the merchantFileTrace value in the Authorization Request XML Message (CWAuthorizationRequest) and Deposit Request XML Message (CWDepositRequest) sent to the service bureau. CWSerenade updates the Reference ID field in the Integration Process Control table with this value. Important: • The Batch Auth File Trace Number can be up to 7 positions for the Paymentech service bureau; however, this number cannot be greater than 3 positions for other service bureaus. Enter 999 in the End number field for this number assignment value to ensure that this number does not exceed 3 positions. • If you are using more than one CWSerenade company, make sure that the Batch Auth File Trace Number for each company has a different number and that the numbers do not overlap. For example, company 1 uses 1-499 and rolls back to 1 again and company 2 uses 500-999 and rolls back to 500 again

Service Bureau Settings

Use the Defining Authorization Services (WASV) menu option to:

• define the service bureaus that you use, such as:

• Authorization services, to authorize charges against a credit card or stored value card.

• Authorization/Deposit services, to authorize card charges and receive deposit amounts.

• Deposit services, to provide settlement for card payments.

• identify the type of service the service bureau performs

• define the parameters that identify your company to the service bureau

• define the information necessary to connect, transmit, and receive data to and from the service, such as:

• the method of communication: Integration Layer (via a CWIntegrate site) or Payment Link (point-to-point)

• if the communication type is Integration Layer, the integration process control job used to transmit data between CWSerenade and the service bureau via a CWIntegrate site

• response codes (vendor responses, AVS responses, and CID responses)

• currency codes

• merchant IDs for individual entities within your company

• whether the order originated as an internet order

Some of the information required to establish a service bureau on your system is provided by the service bureau. For example, each service bureau will assign you a unique password.

Communication Method

The Communication type field for the service bureau indicates how you send transactions between CWSerenade and the service bureau.

• Integration Layer = Transactions are sent between CWSerenade and the service bureau using a CWIntegrate site. Integration layer jobs provide the settings required to send transactions between CWSerenade and the CWIntegrate site; the site maps data to the format of the other system and provides the settings required to communicate with the service bureau.

• Payment Link = Transactions are processed between CWSerenade and the service bureau using a point-to-point integration. Settings in the Interface Properties provide the point-to-point service that is executed and the URL used to connect to the service bureau.

.IL service bureau: To send transactions to the service bureau using CWIntegrate or Point-to-Point communication, create a service bureau using the service code.IL and enter a value in the following fields:

• Application: ATDP (authorization and deposit)

• Merchant ID: INTEGRATION LAYER

• Charge description: CWIntegrate

• Media type: C (communications)

Enter the .IL service bureau in the Primary authorization service field for each service bureau that you create.

Order Types

You define whether an order type is eligible for on-line authorizations and if the order type will display a window during order entry when a response is received from the service bureau, based on the On-line authorization field:

• 1 = the order type is eligible for on-line authorizations and the Select Authorization Response Option Window displays.

• 2 = the order type is eligible for on-line authorization and the Select Authorization Response Option Window does not display.

• 3 = the order type is not eligible for on-line authorization.

See Performing Online Credit Card Authorizations for more information on online authorizations.

Pay Types

Each credit card pay type eligible for authorization should have the service bureau set up as its authorization and deposit service. See Working with Pay Types (WPAY) for more information on setting up pay types.

Pick Slip Generation

If you wish to generate pick slips only for orders that contain pre-paid payment methods and/or credit cards that have received an authorization, you can create a pick slip generation template with the Preauthorized orders only field selected.

Integration Layer Jobs

The following integration layer jobs are used to send authorizations and deposits to a service bureau via a CWIntegrate site. The system uses these integration layer jobs when the Communication type field for the service bureau is Integration Layer.

Integration Layer Job	Description
Online Authorization	When active, the Online Authorization integration layer job generates an Authorization Request XML Message (CWAuthorizationRequest) in online format and sends the message to the service bureau via the CWIntegrate site. The service bureau sends a response to the CWIntegrate site; the site sends a Authorization Response XML Message (CWAuthorizationResponse) back to the integration layer job.
Batch Authorization	When active, the Batch Authorization integration layer job generates an Authorization Request XML Message (CWAuthorizationRequest) in batch format and sends the message to the service bureau via the CWIntegrate site. The service bureau sends a response to the CWIntegrate site; the site sends an Authorization Response XML Message (CWAuthorizationResponse) back to the integration layer job.
Deposit	When active, the Batch Authorization integration layer job generates a Deposit Request XML Message (CWDepositRequest) in batch format and sends the message to the service bureau via the CWIntegrate site. The service bureau sends a response to the CWIntegrate site; the site sends a Deposit Response XML Message (CWDepositResponse) back to the integration layer job.

For each integration layer process, make sure you define:

• an outbound queue manager and queue (if using WebSphere MQ) or connection factory and queue (if using HornetQ) to send the request to the service bureau via the CWIntegrate site.

• an inbound queue manager and queue (if using WebSphere MQ) or connection factory and queue (if using HornetQ) to receive the response from the service bureau via the CWIntegrate site.

Note: You can only define one outbound and inbound queue for each integration layer process. If you create multiple queues, the system sends and receives data in the queue whose Sequence number is 1; all other queues are ignored.

For more information:

• See Working with Integration Layer Processes (IJCT) for more information on setting up an integration layer process.

• See Processing Authorizations and Deposits using CWIntegrate for more information on communicating with a service bureau via a CWIntegrate site.

• See Stored Value Card Overview and Setup for more information on the additional integration layer jobs required for a stored value card pay type.

Notify Property Settings

In order to respond to CWSerenade jobs that may require user intervention to proceed, you must define notify property settings in Working with Cloud Properties (CPRP).

Why would a job require user intervention?

• An error occurred during processing

• The job is used to send transactions to another system and communication failures occur before the transmission completes

Which types of jobs require user intervention?

• Stored Value Card (activation, balance inquiry or authorization reversal)

• Authorization

• Deposit

For more information: See Working with Required Responses (WREQ) for more information on the steps performed when a job requires user intervention.

Property Name	Description
RESPONSE_RETRIES	The number of times CWSerenade looks for a response to a job that requires user intervention before using the default response in order to proceed with the job. For example, if this setting is 5, CWSerenade will look for a user response five times, waiting 60 seconds between each time.
RESPONSE_EMAILS	The list of email addresses that receive the Response Required email when a job requires user intervention. Each email address entered must be separated by a semi-colon (;). For example: email1@add.com;email2@add.com.

Logging Property Settings

CWSerenade writes messages to the RESP.log file when a job requires user intervention. The logging property settings in Working with Cloud Properties (CPRP) define settings for the RESP.log.

Property Name	Description
RESP_FILE_NAME	The name of the file where CWSerenade writes messages when a job requires user intervention. The delivered log file name is RESP.log. If you Use Multiple Application Servers If you use multiple application servers, rename the log so that it identifies the server where the log is located. For example, if you use two applications servers named SERVER1 and SERVER2, rename the RESP log on each server to RESPSERVER1.log and RESPSERVER2.log.
RESP_LOG_LEVEL	The level of logging for the RESP.log. Valid values are: • DEBUG = Generates fine-grained informational events. • INFO = Generates informational messages. • WARN = Generates warning messages. • ERROR = Generates messages that indicate a serious issue. • FATAL = Only generates messages that will cause the application to abort. The delivered logging level is INFO.
RESP_MAXBACKUP_DAYS	The number of days to store an archived RESP.log before it is deleted. The delivered number of days is 30, indicates the system stores one month of RESP.log files. CWSerenade stores one RESP.log per day. Files older than the current day are stored in zip format with the name: RESP.YYYY-MM-DD.log.zip.